Make WordPress Core

Changes between Initial Version and Version 11 of Ticket #32600


Ignore:
Timestamp:
06/22/2015 12:03:53 PM (9 years ago)
Author:
afercia
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #32600

    • Property Keywords has-patch dev-feedback added
  • Ticket #32600 – Description

    initial v11  
    331.
    44Noticed [https://github.com/voldemortensen/menu-customizer/issues/77 during the Menu Customizer development and testing], looks like sometimes the previous message gets announced before the current message.
    5 We couldn't consistently reproduce this so, technically, it's not a bug but [https://wordpress.slack.com/archives/accessibility/p1433787966000781 we agreed in the last accessibility team meeting] to change the aria-relevant value from "all" to the default "additions text".
    6 Basically there's no point in getting also the "removals", at least in this WordPress implementation. Also, see for reference:
    7 http://www.w3.org/TR/wai-aria/states_and_properties#aria-relevant
     5~~We couldn't consistently reproduce this so, technically, it's not a bug but~~ (see comment 1) [https://wordpress.slack.com/archives/accessibility/p1433787966000781 we agreed in the last accessibility team meeting] to change the aria-relevant value from "all" to the default "additions text".
     6Basically there's no point in getting also the "removals", at least in this WordPress implementation. Also, see for reference: http://www.w3.org/TR/wai-aria/states_and_properties#aria-relevant
    87> Note: aria-relevant values of removals or all are to be used sparingly. Assistive technologies only need to be informed of content removal when its removal represents an important change, such as a buddy leaving a chat room.
    98