WordPress.org

Make WordPress Accessible

Updates from September, 2015 Toggle Comment Threads | Keyboard Shortcuts

  • Rian Rietveld 2:09 pm on September 7, 2015 Permalink
    Tags:   

    Accessibility Usertest: Select2 

    In the last 2 weeks @lindsaymac and @helen requested if the Accessibility Team could take a look at Select2.  Select2 is a jQuery replacement for select boxes and gives you a customizable select box with support for searching, tagging, remote data sets, infinite scrolling, and many other highly used options.

    But how accessible is it, and is it accessible enough to include into WordPress core? Some research has been done by Drupal, but there are still issues open on GitHub.

    On the Select2 Github there are examples, styled with bootstrap. To insure we only test the select2 functionality, we made a series of test pages with the minified JQuery and select2.css and select2.js only.

    Examples of Select2 options:

    1. Basic dropdown
    2. Multiple select boxes
    3. Placeholders
    4. Disabled mode
    5. Disabled results
    6. Select with a button
    7. Limiting the number of selections
    8. Hiding the search box
    9. Add choices automatically
    10. For developers: More Select2 examples on GitHub, including bootstrap

    The questions we asked our testers:

    • Can you select an option
    • Can you remove a selected option
    • Is it obvious to you how to select an option
    • If you use a screen reader: did you get sufficient feedback on what was happening
    • What problems did you have trying to select an option

    The testers who joined: Michelle DeYoung, Gabriela Nino de Rivera Torres, Bram Duvigneau, Cyndy Otty, Philip Chalker, Geof Collis, Bart Simons and Andrea Fercia.

    Test results

    1. Basic dropdown

    Example of choices Select2

    Example of choices that don’t get read out, the entered value gets read out instead

    Geof Collis: JAWS 14.5 IE 11.
    Not accessible. I tried to open the box but just got dead air and I found the edit field down the page but was confused on what to do so typed in the letter a and arrowed down to get a list of states only to realize that if I arrowed up and down I got the list I expected in the drop down box.

    Bart Simons: JAWS15 and IE11,  JAWS15 and Firefox, JAWS16 and IE11, JAWS16 and Firefox
    JAWS says “combo box collapsed”.
    I press enter to go to forms mode.
    Since I am told that this is a combobox I try using arrow down to scroll through the list. This does nothing. I can’t go beyond Alaska. Also arrows up, left and right do nothing.
    Then I try to navigate by typing the first letter. This does not work either.

    The test suggestions suggest to use space bar. This is something I would never have tried by myself.
    After pressing space bar, I am told that I am in an edit box. I type “new” and I hear “New Mexico”. Again there is no possibility to use down arrow to go to New York for instance.
    Even New Mexico does not seem to be selected.

    Besides, it is really not intuitive to require a space bar in a combo box.

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.
    The combo box does not respond to Control+Option+Space bar VoiceOver command to open the list of choices. It does respond to the space bar only.

    When the list of choices it’s open, the first element getting the focus is the link to go back to the list of examples. The second element is the search field text and lastly the table with the choices. I’m using Control-Option+right arrow to navigate inside the combo box element.

    The texts for Time zone are ignored by VoiceOver.

    VoiceOver offers me to navigate the table with the choices using Control-Option-right/left arrow or up/down arrow. Both commands worked fine.

    There seems to be something different with the choice Hawaii. There is an intermittent behaviour that requires me to use the Control-Option-right/down arrow command several times before moving to California. It seems like the focus gets stuck on Hawaii choice for some reason.

    It is not possible to move inside the list of choices using only up/down arrows.

    Using only the Enter key will open/close the combo box choices. In this case the first element getting the focus is the search field text. When making a search, the user does not get feedback if the state that she is looking for it is found or not on the list of choices.

    I could not find how to select an option of the list of choices. Normally I’ll use Control+Option+Space bar command, but I don’t get a response. Using Control+Option+Enter does not work either. Using only the Enter key will close the list without selecting the current choice (the one with the focus on it). But if I search for the state and click on Enter, the list will close but the current choice will be selected.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    Keyboard only: Works fine.

    FF/NVDA:
    Forms mode –  The state name is announced. This is considered the label via the aria-labelledby.  The label should be the ‘Select a US state”.
    The text input in the expanded list is not labelled.
    Virtual mode – Can arrow through the items in the combobox, but all that is voiced by NVDA is “blank”.
    Note: Can expand and collapse the list.

    Philip Chalker:  iOS + VoiceOver.
    It all reads fine on the screen

    Cyndy Otty:  iOS + VoiceOver.
    But VO is reading the list, but selection itself is definitely wonky.

     

    2. Multiple select boxes

    Geof Collis: JAWS 14.5 IE 11.
    Not accessible. Entered the box but heard nothing.

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.

    The combo box does not respond to Control+Option+Space bar VoiceOver command to open the list of choices. It does respond to the space bar only.

    Using only the Enter key will open/close the combo box choices. In this case the first element getting the focus is the search field text. The second element getting the focus is the link to go back to the list of examples and lastly the table of choices.

    VoiceOver offers me to navigate the table with the choices using Control-Option-right/left arrow or up/down arrow. Both commands worked fine.

    I could not find how to select a choice directly from the list of choices. Control+Option+Space bar command does not work. Using only the Enter key will send me to the instructions page. But if I search for the state, I’m able to select it using the Enter key after entering the word (although I don’t get any feedback to confirm me if the state I’m looking for was found or not).

    I could not found how to remove a choice. Any of the common VoiceOver commands don’t work to get focus on the selected choices.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    Keyboard only:

    • No visual indicator that it is a select box and offers choices.
    • Yes, selections can be accessed and added.
    • Yes, can remove selections by using the ‘Backspace’. Selection will be removed a letter at a time.

    FF/NVDA:
    Combobox is missing a label. NVDA does announce that it is a combobox.
    List is announced that it is expanded, but the as user arrows through the list the items are announced as “blank”.

    If user randomly selects and item (they will not know what they selected), the items are added to the input field, but they are not announced.
    Unable to access added items in the input to have them announced.  If I assume items exist in that form field, then I can select “Backspace” to remove them a letter at a time.
    Note: Unable to type a selection name in the input field.

    3. Placeholders

    Geof Collis: JAWS 14.5 IE 11.
    Semi accessible. I expected that I would hear the placeholder before going into forms mode but had to enter the field before I did.

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.
    No, VoiceOver did not announce the placeholder inside the first option. The combo box does not respond to Control+Option+Space bar VoiceOver command to open the list of choices. It does respond to the space bar and Enter key.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    FF/NVDA: Yes, Placeholder is announced. (No labels for input fields)

    4. Disabled mode

    Geof Collis: JAWS 14.5 IE 11.
    Semi accessible. I expected a checkbox for the modes but realized to click on the button and it worked but I’m starting to wonder if I should be reading 2 drop down menus because that is what I am getting in all examples so far.

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.
    I was able to enable and disable the two select boxes. It does work with Control-Option-espace bar and with the Enter key.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    Keyboard only: Yes, Enable/Disable buttons work

    FF/NVDA:

    • No labels.
    • Yes, Enable/Disable buttons work.
    • Tabbing backwards through the inputs after ‘Disable’ has been selected skips over the inputs initially, but if user continues one more tab backwards the 2nd input will be announced, “Combobox collapsed has autocomplete”.

    5. Disabled results

    Geof Collis: JAWS 14.5 IE 11.
    Not accessible. Sometimes it reads first and other times it doesn’t it isn’t consistent and I only get one box. Used the back button and it froze my browser and had to close it down, grrr!

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.
    I’m not able to move from the first option. I’m using Control-Option-right arrow to navigate between the options on the table. Using only right/left/up/down arrow to move from one option to the other won’t work.

    If I interact with the table choices (Control-Option-shift-down arrow) I’m able to move to the second option and it will be announced by VoiceOver. From the second option it is impossible to move to the third option.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    Keyboard only:

    • No labels for inputs.
    • Yes, disabled item is skipped over when arrowing.
    FF/NVDA:
    • List items are announced as “blank”.
    • Yes, disabled item is skipped over when arrowing.

    6. Select with a button

    Geof Collis: JAWS 14.5 IE 11.
    Semi accessible. But I find all of these boxes confusing and verbose so I’m quitting, I dont like it in the least, time to go back to the drawing board. :O)

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.
    Yes I can set the option in the select drop using the two buttons for each example. In both examples, VoiceOver does not give feedback after the setting function. I’m able to press the buttons using Control-Option-space bar, only the space bar key and the Enter key.

    Also it is possible to open/close the select choices using Control-Option-space bar, only the space bar key and the Enter key. I think those two examples are easiest to use with VoiceOver.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    Keyboard only:

    • 1st Example: ‘Set’ & ‘Init’ work, but the others do not.
    • 2nd Example: Yes, it works.

    FF/NVDA:

    • 1st Example: ‘Set’ & ‘Init’ work, but the others do not.
    • 2nd Example: Yes, it works.   Note: Selected items are not announced in the input field they are added to.

    7. Limiting the number of selections

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.
    I was not able to select any of the choices. Once in the table choices I tried selecting with the Enter key (it sent me back to the instructions page), using space bar key only and Control-Option-espace bar did not work either.

    The combo box does not respond to Control+Option+Space bar VoiceOver command to open the list of choices. It does respond to the space bar key and the Enter key.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    Keyboard only: Yes, it works.

    FF/NVDA:

    • Yes, can only select two items.
    • No, the feedback is not announced.
    • No, the item choices are not announced.
    • No, selected items are not announced.

    8. Hiding the search box

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.
    The search box it is very well hidden, VoiceOver did not notice it.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    Keyboard only: Yes, it works.
    FF/NVDA: Yes, Search box is hidden and not voiced by screen reader.

    9. Add choices automatically

    Gabriela Nino de Rivera Torres: VoiceOver+Safari.
    I was able to add choices using the coma and the space. The combo box does not respond to Control+Option+Space bar VoiceOver command to open the list of choices. It does respond to the space bar key and the Enter key.

    Michelle DeYoung: Windows 8.1 / FF 40.0.3 / NVDA 2015.2
    Keyboard only: Yes, it works.
    Note:
    Using space – Cannot add more than two rows of items.
    Using comma – Cannot fill past one row of items.

    FF/NVDA:
    Yes, can add items with space or comma, and they will appear in the list.
    If too many items are added to the list they are dynamically removed except for the first item.
    >Note:
    Using space – Cannot add more than two rows of items, but NVDA will still voice like items are being added.
    Using comma – Cannot fill past one row of items, but NVDA will still voice like items are being added.
    Items – Items in list are announced as “blank”.  Items added to the input are also not announced.

    Notes from Bram Duvigneau

    I had a quick look at Select 2 using Firefox + latest NVDA nightly build.

    The Select 2 widget is announced as combo box, however it doesn’t respect the common keyboard navigation conventions on Windows. I expect to be able to use the arrow keys to select an item when the select box is in closed state, that doesn’t work. The alt+down arrow hotkey, which is the default to open a dropdown in Windows, works. However, when the select box is open, the active item is not announced by a screenreader. I can select an option by pressing enter and after closing the box the selected item is readable.

    Conclusions: It seems that some aria support has been implemented. This causes a screenreader to pick up the role (select box) and the state (open/closed).
    However, much more work is needed to support the focus in an open Select 2 widget. All the special Select 2 features such as grouping items and typing to filter/search the list has not been tested, but this also needs additional aria markup to be read by screenreaders.

    Another issue is the expected keyboard shortcuts. These are different on every platform and Select 2 should feel native on all of these platforms, so this has to be implemented and tested prety well. E.g. on Windows I don’t expect a dropdown to open when I press space bar, but on Mac this is the common way to open such an element.

    Notes on the test results by Andrea Fercia

    • Difficult to understand how to open the combo box. Users expect to open the combo box using just the down arrow key. Previous version worked that way.
    • Missing label for the input field (The text input in the expanded list is not labelled). It gets announced with the name of the first option, e.g.: “Alaska  combo box  collapsed  has auto complete”. Investigate on current usage of “aria-labelledby”.
    •  Searching:
      • leaving the field empty, it is possible to arrow through the items in the list but every option gets announced as “blank”
      • entering some charavters e.g. “mi” and arrowing through the results e.g. “Minnesota”, “Mississippi”, “Missouri” will read out just “mi” which is the entered value in the input
      • no feedback about how many search results – the previous version announced “5 results are available, use up and down arrow keys to navigate” or “No matches found”.
    • “I could not find how to select an option of the list of choices”. I guess that’s because all you hear is “blank” or the characters you entered in the search field.
    • No feedback when selecting an item: If user randomly selects and item (they will not know what they selected), the items are added to the input field, but they are not announced.
    • Multiple select boxes: “Unable to access added items in the input to have them announced.  If I assume items exist in that form field, then I can select “Backspace” to remove them a letter at a time.”Once you’ve added options, they’re not announced so users really have to guess they’re in the input field.

    Conclusion

    The main problems are:
    • There is no or not enough feedback for screen readers on what is selected or what can be selected (list items are announced as “blank”.)
    • No feedback about how many search results.
    • The select dropdown does not behave like a user expects, quoting Bart: “It is really not intuitive to require a space bar in a combo box.This is something I would never have tried by myself”
    • Testers report slightly better results on iOS + VoiceOver
    • Select2 has at the moment too many accessibility issues to be included into WordPress core
     
    • Rian Rietveld 2:19 pm on September 7, 2015 Permalink | Log in to Reply

      Updated the test results for iOS + VoiceOver by Cyndy Otty and Philip Chalker

    • Rian Rietveld 6:11 am on September 8, 2015 Permalink | Log in to Reply

      @joedolson opened an issue about this test result on the Select 2 GitHub: Accessibility issues in Select2: https://github.com/select2/select2/issues/3744

    • Graham Armfield 8:56 am on September 8, 2015 Permalink | Log in to Reply

      This is an impressive test and presentation of results – well done everyone.

      I’ve been doing some testing recently with Dojo UI components and Dragon NaturallySpeaking voice recognition software, and that testing has underlined some real accessibility issues when controls try to emulate select elements.

      I will endeavour to find some time in the next couple of days to test out Select2 with Dragon, and circulate the results.

    • chriscct7 1:31 pm on September 8, 2015 Permalink | Log in to Reply

      Fantastic job guys. I’ll help monitor the ticket where I can and update the trac tickets currently blocked on Select2

    • NateWr 3:16 pm on September 8, 2015 Permalink | Log in to Reply

      This kind of results reporting is eye-opening. Thanks for the detailed write-up.

    • Aaron Jorbin 10:30 pm on September 9, 2015 Permalink | Log in to Reply

      Thanks to all the testers. Very impressive work here. Irregardless of if WordPress will include select2, hopefully these results inform the Select2 team and help them create a better, more accessible product. Has anyone sent these results over to them or otherwise alerted them so that they know about the findings?

    • Rian Rietveld 7:11 am on September 10, 2015 Permalink | Log in to Reply

      Hey Aaron, yes, @joedolson opened an issue on the Select2 GitHub: https://github.com/select2/select2/issues/3744 which was received well and commented on and we even invited Mike Gifford from Drupal to join the discussion.

    • Graham Armfield 7:46 am on September 11, 2015 Permalink | Log in to Reply

      Yesterday I did some testing of Select2 using Dragon NaturallySpeaking – voice recognition software used by many people with motor impairments, and here are my results.

      I was using Dragon 14 Professional on Windows 8.1 with IE11. Dragon 14 (like Dragon 13 before it) features some support for ARIA although that is still evolving.

      Basic Dropdown

      The control looks like a dropdown but Dragon does not recognise it as such. Command “Click List Box” does not cause the control to be selected as would be expected with a real select box. “Click combo box” does not select the control either – technically it’s not a true combo box but you can type to refine search so I thought I’d try that.

      It is possible to “tab” to the control from other items, although “shift-tab” seems flaky.

      When focus is on control the commands “Show Choices” and “Expand List” do work as expected, although “Hide Choices” does not close up the selections as expected.

      It is also possible to use the “Mouse Grid” commands to click on the item – which opens up the list of choices. When the options are shown, it is possible to voice a state name and have that state name shown. Voicing an option that is not in the list does give the ‘No results found’ message.

      When options are shown it is possible to move through the options using the “Move down” or “Move up”. I can select an item by saying “Press Enter”. The list is collapsed.

      Multiple Select Boxes

      The Control look like a text box as there is no arrow icon associated with it. It is not obvious that I can select multiple items – presumably a label would prompt that.

      “Click Type Text” does work here so Dragon thinks it’s a text box. “Click List Box” does not work.

      It seems not to be possible to “shift-Tab” into the control with Dragon. But forward tabbing seems to work OK.

      Once the ‘select’ is open, as before I can use “Move Up/Down” commands to move through options and “Press Enter” to select one.

      Speaking the state name does not work properly though – only the last letter of the word I said is shown, and the state is not highlighted. The full word is present though – saying “Backspace” reveals the rest of the state name minus the last letter. Usually the state name you want is featured in the list below.

      To select multiples states with Dragon is possible, but you need to treat each additional state as a separate interaction.

      Trying to delete previously selected items using “Backspace” doesn’t work well at all in Dragon. You get partial state names, and for some reason Dragon will consistently interpret multiple “Backspace” commands as a command to go back to the previous page. This does not happen when interacting with text in normal text boxes.

      Actually it seems there is no way to delete previously selected items with Dragon. Using “Mouse Grid” or “Mouse Move” commands to home in on the small x (a very small click target) is possible, but then when the “Click” commands are spoken, the item ‘hovered’ over is not removed and the cursor is placed after the last previously selected item. With “Press Click”, the words appear in the text box. Somehow the control is interfering with how Dragon operates.

      Placeholders

      Not relevant for Dragon.

      Disabled Mode

      Yes I can enable/disable controls using the buttons in Dragon.

      Disabled Results

      The second option is missed out when I command Dragon to move up and down through the selection. So works OK.

      Select with a button

      I can issue commands to press the buttons OK and the desired result is achieved. However, when I mouse click any of the buttons they turn blue – this doesn’t happen when actioning the buttons with Dragon.

      Limiting the number of selections

      Yes that works OK

      Hiding Search Box

      Works OK

      Add choices automatically

      This doesn’t work well.

      I only seem to be able to interact with the control if I emulate clicking on it – using Mouse Grid. Tabbing to the control gives me the focus indication, but I can’t interact with the control until I emulate clicking on it.

      Clicking on the field opens up the list of options. I can select them successfully as with multiple select boxes.
      However, when I speak an option I run into the same problem as earlier, only the last letter of what I’ve spoken is shown – along with the same issues with backspacing.

      Issuing the “press enter” command does show what I have spoken, but when I “tab” away from the field my input disappears.

      Summary

      Most functionality is available to Dragon users when using the full variety of voice commands available, although it is not as straightforward as using native HTML controls – since they can’t always be referenced by type.

      However, deleting previously selected items is not possible with Dragon 14 using the Multiple Select functionality, and when adding choices automatically.

      The Add choices automatically functionality cannot be used either.

    • Rian Rietveld 7:53 am on September 11, 2015 Permalink | Log in to Reply

    • Sharon Austin 1:48 pm on September 11, 2015 Permalink | Log in to Reply

      This report….is a thing of beauty. Love it.

  • Joseph Karr O'Connor 6:27 am on June 20, 2014 Permalink  

    Accessibility Team Update: June 18, 2014 

    Visual Focus In Left Navigation

    Screenshot of admin left navigation showing Posts menu selected with New Post submenu selected

    Posts menu selected with indistinguishable darker black shading, Add New sub menu item selected with text in dark blue. Note that dark blue text against dark gray is hard to see.

    Color Alone

    Visual focus indicators for wayfinding are relied on heavily by some keyboard-only users. @helen notes the enhanced visual focus indicators now in trunk. Ticket #28267 needs a lot more work bringing the focus style to various places but one area that needs a smart solution is left navigation. Now we are relying on color changes which are, in some instances, too subtle. Indeed, color is not to be used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

    Suggestions

    We discussed this for most of the meeting and here are some suggestions.

    • Helen reports that a blue glow does not look good
    • White outline around menu item with white outline also around selected submenu item
    • Reversing the colors with another undefined indicator element
    • Triangle to the left of main menu item and selected submenu item
    • Underline under main menu item and selected submenu item (might be mistaken for links)

    Solution Needed

    We need some suggestions for an elegant solution. Bear in mind that there are eight admin color schemes and any solution should take that into account. I have created ticket #28599 to work on this issue. A WordPress Accessibility Team shirt to the person who comes up with the adopted solution!

     
    • jebswebs 5:02 pm on June 20, 2014 Permalink | Log in to Reply

      Just wonder if one of the eight admin color schemes could be called High Contrast and use a yellow on black color set. I have been battling the gray on white and gray on black fight with multiple theme developers in multiple CMSs for several years. It would be curious to know how many users ever take time to change from the Default admin color scheme.

      • esmi 7:12 pm on June 20, 2014 Permalink | Log in to Reply

        Helen and I have talked briefly about this before. The idea was that, as the admin skinning system matured, there would be more opportunities to provide low and high contrast admin skins via plugins, if necessary. It’s certainly something I’ve been wanting to do for years.

    • esmi 7:08 pm on June 20, 2014 Permalink | Log in to Reply

      I’m a big fan of reversing background and foreground colors, so in the example screenshot you posted above, I’d want to see something like a blue background with black/dark grey text.. It’s got to really “pop” for sighted keyboard navigators. triangle indicators are very nice as added features for onhover but I’d argue that they’re too subtle for focus highlighting. Ditto for underlines. General rule of thumb: if you have to visually hunt for the currently focused element, then you need something else.

      • Joseph Karr O'Connor 9:35 pm on June 20, 2014 Permalink | Log in to Reply

        So you and @jebswebs support a high and a low contrast admin color scheme which is a different path from devising a solution just for the left navigation that persists through all color schemes? I’m very interested in this idea, wonder if enough people will discover the feature. I think we still need robust focus indicators throughout admin, but support additional accessibility color schemes.

    • David A. Kennedy 2:35 pm on June 25, 2014 Permalink | Log in to Reply

      As I’ve said in our previous team meetings, I’m in favor of a suitable baseline for all color schemes. Although, I love the idea of specialized high contrast themes in addition to that.

  • Joseph Karr O'Connor 3:57 am on June 12, 2014 Permalink  

    Accessibility Team Update: June 11, 2014 

    New Accessible Theme

    Joe Dolson is working on a new accessible theme for the Cities series using an innovative modular approach for accessibility by gathering up accessibility concepts into separate files.

    Joe says:

    “I’m explicitly placing all the accessibility-specific code into a11y.php and a11y.js, to make them easy to find. This is intended to be a useful resource for theme developers, so I want everything to be easy to find.”

    Also of note is skiplinks.js which fixes a bug in WebKit. Simply using an anchor link for the skiplink isn’t enough for WebKit, because keyboard focus will not follow visual focus without Javascript. Joe will be presenting this new theme in a session at WordCamp Chicago this weekend.

    Accessibility Theme Check Process Enhanced

    We are aware that a few themes that are not accessible have arrived in the theme directory with the #accessibility-ready tag. Perhaps the theme creators misunderstood the tag or copied it from another theme without thinking. We got a message from someone who knows accessibility that he bought a theme based on the fact that the free version has the #accessibility-ready tag. Expecting it to be accessible, he was disappointed. Contacting the theme creator he found out that they will be uploading a new free version without the tag.

    Joe Dolson on the process:

    “We’re still struggling with themes getting through the process without getting audited, but we have a recourse for this now. The official policy is to give the author notification that their theme needs to go through the accessibility-ready review to keep the tag, and that they have 72 hours to begin rectification – either by uploading a new version without the tag or by uploading a new version that will begin the process of meeting the accessibility-ready requirements. After 72 hours without a response, the theme will be suspended from the theme repository.”

    Unification of Visual Focus Indication

    It is essential to provide a visual cue to sighted keyboard-only users letting them know where they are on the page. There is no standard look for visual focus indicators. The issue is made more complex because user agents approach this in different ways. @helen talked with us last week and this week again about the fact that the visual look of focus indicators is not unified, and in some instances is not perceivable. For example, on the Media Library screen this is a screenshot showing “apply” button with dotted line focus indicator active and it is not perceivable. One tab press to the right of the “apply” button is the “All dates” select menu selected with a screenshot showing “All dates” select menu with blue glow and dotted line.

    The base look might be the approach taken by WebKit, a blue glow. A base look with more than one element is what we seek. Even if the color blue cannot be perceived there is still the glow. This week we have a goal of organizing the approach to the UI in such a way that the visual focus indicators are unified and perceivable.

     
    • _Redd 8:37 pm on June 18, 2014 Permalink | Log in to Reply

      Hi, everyone, regarding the Unification of Visual Focus Indication, and the meeting today (June 18), I found an example of what I was talking about with using icons to demonstrate a change of focus in the left-hand nav menu.

      http://tympanus.net/Development/IconHoverEffects/#set-1

      Here, the icons “reverse” dark and light areas, and also have additional visual indicators that show the item has received focus. A picture is worth a thousand words, and this example says it far better than I could.

    • _Redd 8:53 pm on June 18, 2014 Permalink | Log in to Reply

      Whoops! Follow Up!

      These icons undergo changes when hovered over, not when receiving focus. The idea of course is that we could develop css to perform similarly when the item receives focus.

  • Graham Armfield 11:30 am on November 28, 2013 Permalink
    Tags: , ,   

    Analysis of what gets into the alt and title attributes when adding an image into a page/post 

    There was some debate in last night’s IRC chat about trac ticket 26270 raised by @yaelkmiller. Her original point was that when adding images to pages and posts, the Alt text box should have more prominence than the Title box – the alt attribute being an important accessibility feature.

    Personally, I think the idea is a good one, but discussion and comments by @helen also revealed some interesting behaviour when inserting images concerning what text ends up in the title attribute of the image, and what text ends up in the alt attribute.

    I’ve done a series of tests using different use cases and they are presented in the tables below – including my expected results and the actual results.

    Uploading images

    Test No. Use Case Graham’s Expected Result Actual Result in Page
    1 Upload image, add it to page with no change to Title box or Alt text box Title attribute set to image name minus suffix Title attribute absent, alt attribute set to image name minus suffix – ie what the Title box was set to
    2 Upload image, add it to page but change Title box, not Alt text box Title attribute set to amended value Title attribute absent, alt attribute set to amended Title box value
    3 Upload image, add it to page but change Alt text box, not Title box Title attribute set to image name minus suffix, alt attribute set to amended value Title attribute absent, alt attribute set to amended Alt text box value
    4 Upload image, add it to page but change both Alt text box and Title box Both title and alt attributes set to amended values Title attribute absent, alt attribute set to amended Alt text box value

    Using images from media library (previously uploaded) without amendment

    Test No. Use Case Graham’s Expected Result Actual Result in Page
    5 Add image from media library that has Title box set but not Alt text box Title attribute set but not alt Title attribute absent, alt attribute set to whatever Title box was before
    6 Add image from media library that has Alt text box set but not Title box Alt attribute set but not title Alt attribute set but not title
    7 Add image from media library that has both Title box and Alt text box set Both attrubutes set Title attribute absent, alt attribute set to whatever Alt text box was before
    8 Add image from media library that has neither Title box nor Alt text box set Title attribute absent, alt attribute empty Title attribute absent, alt attribute empty

    Using images from media library (previously uploaded) but making amendments

    Test No. Use Case Graham’s Expected Result Actual Result in Page
    9 Add image from media library, that has just Title box set, update Title box Title attribute set but not alt Title attribute absent, alt attribute set to whatever Title box was amended to
    10 Add image from media library, that has just Alt text box set, update Alt text box Alt attribute set but not title Title attribute absent, alt attribute set to whatever Alt text box was amended to
    11 Add image from media library, that has neither Title box set nor Alt text box set, update Title box Title attribute set but not alt Title attribute absent, alt attribute set to whatever Title box was amended to
    12 Add image from media library, that has neither Title box set nor Alt text box set, update Alt text box Alt attribute set, no title attribute Title attribute absent, alt attribute set to whatever Alt text box was amended to
    13 Add image from media library, that has both Title box and Alt text box set, update Alt text box Both attributes set Title attribute absent, alt attribute set to whatever Alt text box was amended to
    14 Add image from media library, that has both Title box and Alt text box set, update Title box Both attributes set Title attribute absent, alt attribute set to whatever Alt text box was originally set to

    Looking at the results

    Using the Add Media Panel to insert an imageThe first revealing thing about these tests is that my own view of how I thought WordPress worked is at odds with the actual results in most cases.

    The second thing that’s become obvious is that it’s actually impossible to set the title attribute for an image whilst using the Add Media panel. The title attribute never appears in any of the results.

    Actually the only way to set a title attribute image within pages and posts is to use the older image edit dialogue box once the image is placed within the page (or to manually update the HTML obviously).

    I think the confusion comes from the labeling of the Title input field in the Add Media Panel. Helen refers to this in her comments on the trac ticket I believe. Maybe to avoid confusion this box should be given another label – ‘Image name’ maybe. I confess that I hadn’t noticed this change in WordPress behaviour – it did used to be possible to directly influence the title attribute of an image when uploading and adding it to a page/post.

    I’m sure that I’m not the only one who didn’t appreciate this situation. There is a plugin called Shutter Reloaded that I’ve seen on a couple of sites, which uses the title attribute from the image to provide a caption beneath the image when the full size is shown. Obviously this plugin is broken if site admins don’t realise the title attributes aren’t being written into the <img> tags – and the plugin author perhaps doesn’t realise either. I can’t comment on other lightbox plugins.

    What do you think? Is this what you expected? Is this the right way to go?

     
    • Rian Rietveld 3:23 pm on November 29, 2013 Permalink | Log in to Reply

      Hi Graham,
      The addition the title attribute to the element img was removed a few versions of WordPress ago, which is a improvement to my opinion.

      I use the title only for labeling the images in the Media Library, yes, maybe image name is a better description for that input field.

      And it seems logical to add the images name into the alt field if the alt field is empty, but that can result in alt texts like IMG_123. Maybe the best way is to leave the alt text empty unless a user entered a value there.
      An alt=””is always better than an alt=”IMG_123″.

      Rian

  • esmi 9:42 am on January 25, 2013 Permalink
    Tags: , ,   

    IRC Meetups 

    Most of the other WordPress groups have weekly meetings via IRC. Do you think this would be viable option for this group too? Does anyone have any difficulties accessing IRC?

    If we did have regular meetups, I’m assuming weekdays would be best — for half an hour or so between 19:00 and 21:00 GMT?

    Thoughts

     
    • GrahamArmfield 9:50 am on January 25, 2013 Permalink | Log in to Reply

      Sorry for my ignorance but what’s IRC?

      • esmi 10:38 am on January 25, 2013 Permalink | Log in to Reply

        Oh – sorry! Internet Relay Chat. You can use dedicated software like mIRC. There are also JavaScript browser interfaces like Freenode’s web chat and an increasing number of apps for mobile devices. I’m about to try using IRC999 for the iPad which, I understand, works well with VoiceOver.

    • GrahamArmfield 9:51 am on January 25, 2013 Permalink | Log in to Reply

      Re your second question – yes, weekdays are best.

    • ceo 11:39 am on January 25, 2013 Permalink | Log in to Reply

      I have no problem with IRC. I’m on it all day for work anyway. 😉

      • ceo 11:40 am on January 25, 2013 Permalink | Log in to Reply

        Ok, not related, but the last two days (and I assume this may be related to being invited?) when I post a comment it gives me an “unknown error; comment not posted” message even though my comment has too been posted.

      • Joseph Karr O'Connor 9:03 pm on January 25, 2013 Permalink | Log in to Reply

        I will participate in IRC sessions, very smart idea.

    • Nelson 12:48 pm on January 25, 2013 Permalink | Log in to Reply

      I haven’t used WordPress’s IRC before, but I think using IRC in that time frame to discuss accessibility testing would be an excellent idea.

    • Sveta 2:31 pm on January 25, 2013 Permalink | Log in to Reply

      Chat is a good idea as long as its FULLY accessible to deaf participats like myself via text.

      • esmi 2:35 pm on January 25, 2013 Permalink | Log in to Reply

        @Sveta: It’s 100% pure text. I have hearing problems myself and absolutely hate video chat. 🙂

        • Sveta 3:18 pm on February 6, 2013 Permalink | Log in to Reply

          Yes, but some chats include audio and people like myself can miss it if people use audio and don’t type.

    • esmi 2:32 pm on January 25, 2013 Permalink | Log in to Reply

      That could just be P2 (the theme) acting up. Sometimes it tells me that the network connection has been lost and then quite happily publishes my Post or comment. :-/

      • ceo 4:23 pm on January 25, 2013 Permalink | Log in to Reply

        Assuming this was to me? 🙂
        Okies, well, I won’t freak out then about random posting errors that aren’t errors per se.

    • Ipstenu (Mika Epstein) 4:13 pm on January 25, 2013 Permalink | Log in to Reply

      esmi – You’re welcome to snag sfd for that. I mean, docs does. 🙂 Or use UI, since I think they’re mostly in -dev now.

    • esmi 4:21 pm on January 25, 2013 Permalink | Log in to Reply

      Re-using UI would be a great idea. Who would I need to clear this with?

    • Joseph Karr O'Connor 9:45 pm on January 25, 2013 Permalink | Log in to Reply

      For our first IRC topic:

      From rachelbaker a new post:
      Theme Handbook Update Jan 24th on documentation page:
      https://make.wordpress.org/docs/2013/01/24/theme-handbook-update-jan-24th/

      It calls for contributions on many topics including accessibility. I just saw this and have not had time to read the Google docs associated with the project. If there is a need I will contribute and will ask for input from this group.

    • esmi 9:53 pm on January 25, 2013 Permalink | Log in to Reply

      I’ve already volunteered to contribute the the Theme Handbook (or pretty much any other handbook that is to have an Accessibility section) . I figured I’d draft something up and then throw it open to this group for comments, suggestions etc.

    • Joseph Karr O'Connor 11:20 pm on January 25, 2013 Permalink | Log in to Reply

      Excellent, if you want my help I’m ready.

    • Joe Dolson 8:55 pm on January 26, 2013 Permalink | Log in to Reply

      I could give a shot to IRC chat most week days.

    • Rian Rietveld 7:44 am on January 28, 2013 Permalink | Log in to Reply

      I’d like to join in too, for me on week days is also the best.

    • Amanda 6:02 pm on February 1, 2013 Permalink | Log in to Reply

      I would love to participate in some sort of WP accessibility meetup. Weedays would be best for me too.I’m using both Jaws and NVDA, and Window Eyes on occasion, have been woring with WordPress since 2005 helping people set up accessible websites with it, and have been looing for a way to contribute to WP development.

    • tady 11:39 am on February 6, 2013 Permalink | Log in to Reply

      Yup, I’d be all up for being involved in that. I haven’t been able to give constant feedback to the group due to work, and only dipping in and out of the group page, so I’d be glad to contribute to an IRC group more regularly.

    • Sveta 3:17 pm on February 6, 2013 Permalink | Log in to Reply

      I wonder what WordPress managers say about this? Is it possible to bring this issue to attention of managers?

      • esmi 3:37 pm on February 6, 2013 Permalink | Log in to Reply

        Sorry – I’m not following you. There are no WordPress managers per se. It’s a community project and we should be able to use the existing #wordpress-ui channel. I’m just about to post a suggested schedule.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Skip to toolbar