Accessibility skin design
Posted: Thu Mar 19, 2020 6:02 pm
Just had this email from existing client - due to book in a reshoot early summer to add more scenes into a campus-wide university virtual tour - and they've come back with this statement - most of which I don't understand or think isn't even easily feasible in Pano2VR - your collective thoughts?
"The other challenge we have is that we need to ensure our website and all assets are accessible, with the new accessibility guidelines for the public sector we need to ensure the tour meets these guidelines which need to be in place for September (if not ready we may need to remove the tour until it is ready). Our webteam have provided the following must-have features for the tour.
• Make sure everything works for keyboard-only users
• Use descriptive titles for pages and frames
• Use descriptive links so users know where the link will take them
• Implement ACTIVE FOCUS for keyboard users
• Make it easy for users to disable and change shortcut keys
• Provide ALT TEXT for non-text content
• Make sure content can be navigated and read by a screen reader
• Use the proper mark-up for every feature, so the relationship between content are defined properly
• Use text colours that show up clearly against the background colour
• Make sure user can resize the text
• Make sure every feature can be used when text size is increased by 200%
• Make sure the user can navigate using voice commands
• Not use images of text
• Use valid HTML so assistive technologies can accurately interpret and parse content
• Make sure the code lets assistive technologies know what every user interface component is for, what’s state is currently in and if it changes
I'm thinking it'll be easier to walk away from the whole project!!!
Stu
"The other challenge we have is that we need to ensure our website and all assets are accessible, with the new accessibility guidelines for the public sector we need to ensure the tour meets these guidelines which need to be in place for September (if not ready we may need to remove the tour until it is ready). Our webteam have provided the following must-have features for the tour.
• Make sure everything works for keyboard-only users
• Use descriptive titles for pages and frames
• Use descriptive links so users know where the link will take them
• Implement ACTIVE FOCUS for keyboard users
• Make it easy for users to disable and change shortcut keys
• Provide ALT TEXT for non-text content
• Make sure content can be navigated and read by a screen reader
• Use the proper mark-up for every feature, so the relationship between content are defined properly
• Use text colours that show up clearly against the background colour
• Make sure user can resize the text
• Make sure every feature can be used when text size is increased by 200%
• Make sure the user can navigate using voice commands
• Not use images of text
• Use valid HTML so assistive technologies can accurately interpret and parse content
• Make sure the code lets assistive technologies know what every user interface component is for, what’s state is currently in and if it changes
I'm thinking it'll be easier to walk away from the whole project!!!
Stu