This is an idea that hit me I wanted to share with the work group.
Today modern web browsers and video smartphone apps offer 'picture in picture' feature. It allows me to take a video element in the viewport and detach it from its location so it floats while I continue surfing. Whether or not this is useful can be debated, however I wanted to share it as an example of a browser-offered 'accessibility' feature.
Perhaps a simpler example is when the browser offers a video player scrub bar and play/pause/stop controls over a video element. (I must admit, I have ALWAYS wanted this for animated pictures like GIF!)
Another example, not provided by the web browser, but by some e-commerce platforms is the ability to show a zoomed part of the image when hovering over it with the cursor, inside a floating 'magnifier' box that appears besides the image when hovering.
Another example, offered by some websites and not the web browser, regards data tables. Some websites allow you to sort rows by clicking on a column header. For long tables that require scrolling, some platforms may retain the header column floating as you scroll. Some may allow you to filter table data through queries entered at header column.
Another accessibility feature offered by BOTH web browsers and some websites is: dark/light mode themes.
OK, I gave the examples; what am I trying to propose?
I would like to argue that, accessibility features, could be provided by: the web browser (through generic features), or by the content author (through interactive UI features), or by both.
When the web browser implements generic accessibility features, it allows the user for a 'universal' UI for the user when dealing with contents.
When the content author provides accessibility features and UI conveniences, it is more specific to that content and tailored to it.
When both offer, it could be a clash.
Am I recommending any particular approach? Not really. However, I wanted to share this insight if any of the working group members find it useful.
Thank you for your dedication towards accessible content 💫
This is an idea that hit me I wanted to share with the work group.
Today modern web browsers and video smartphone apps offer 'picture in picture' feature. It allows me to take a video element in the viewport and detach it from its location so it floats while I continue surfing. Whether or not this is useful can be debated, however I wanted to share it as an example of a browser-offered 'accessibility' feature.
Perhaps a simpler example is when the browser offers a video player scrub bar and play/pause/stop controls over a video element. (I must admit, I have ALWAYS wanted this for animated pictures like GIF!)
Another example, not provided by the web browser, but by some e-commerce platforms is the ability to show a zoomed part of the image when hovering over it with the cursor, inside a floating 'magnifier' box that appears besides the image when hovering.
Another example, offered by some websites and not the web browser, regards data tables. Some websites allow you to sort rows by clicking on a column header. For long tables that require scrolling, some platforms may retain the header column floating as you scroll. Some may allow you to filter table data through queries entered at header column.
Another accessibility feature offered by BOTH web browsers and some websites is: dark/light mode themes.
OK, I gave the examples; what am I trying to propose?
I would like to argue that, accessibility features, could be provided by: the web browser (through generic features), or by the content author (through interactive UI features), or by both.
When the web browser implements generic accessibility features, it allows the user for a 'universal' UI for the user when dealing with contents.
When the content author provides accessibility features and UI conveniences, it is more specific to that content and tailored to it.
When both offer, it could be a clash.
Am I recommending any particular approach? Not really. However, I wanted to share this insight if any of the working group members find it useful.
Thank you for your dedication towards accessible content 💫