Changes between Initial Version and Version 1 of Ticket #28858
- Timestamp:
- 07/12/2014 06:11:19 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28858 – Description
initial v1 1 1 1) Button to move forward has no text. There needs to be some kind of text in the step button for screen reader users to know what's happening. Patch adds text 'Set'. 2 2 3 2) Focus is being manipulated so that radio buttons can only be navigated when fieldset is focused, but the fieldset can't receive focus from the keyboard. Patch adds tabindex='-1'so that the fieldset can receive focus.3 2) Focus is being manipulated so that radio buttons can only be navigated when fieldset is focused, but the fieldset can't receive focus from the keyboard. Patch adds `tabindex='-1'` so that the fieldset can receive focus. 4 4 5 3) Languages are written in native language, but have no lang attribute to inform screen reader how to pronounce the language. Patch adds lang="$language['language']"-- this will not be complete, because the WP language profiles do not match the ISO 639 language code list http://www.loc.gov/standards/iso639-2/php/code_list.php. Might be a good idea to set up a language reference so that these can be mapped appropriately.5 3) Languages are written in native language, but have no lang attribute to inform screen reader how to pronounce the language. Patch adds `lang="$language['language']"` -- this will not be complete, because the WP language profiles do not match the ISO 639 language code list http://www.loc.gov/standards/iso639-2/php/code_list.php. Might be a good idea to set up a language reference so that these can be mapped appropriately. 6 6 7 7 4) For sighted keyboard users, navigating the language list does not trigger scrolling in the language container. This means that any user who can't use a mouse to navigate the list will not be able to select their language if it's outside the default visible options. Needs: trigger scrolling one keypress. And I'm not sure how to do that.