The annotations should just work once screen reader support is added. For the moment, you can see the annotations data being exposed with tools like Firefox Accessibility Inspector. Unfortunately, you won't be able to use any of these yet, as screen reader support is currently not there. Chrome from version 81 onwards, currently behind the #enable-accessibility-expose-aria-annotations flag (go to chrome://flags to enable this.).Firefox from version 75 onwards, on Windows and Linux (on macOS, we are first waiting for Apple to define what Safari will expose as Apple-dialect attributes to VoiceOver, and will then follow suit.).aria-details has been updated so that it can support multiple IDs - this makes sense, for example you can easily envisage having multiple comments relating to the same bit of text.ĪRIA annotation roles and objects are currently exposed in: To provide a semantic association between the document content being annotated and the annotation, an aria-details attribute can be set on the annotated content that contains the ID of the annotated element. role="comment" - semantically denotes a comment/reaction to some content on the page, or to a previous comment.This should be used on an element that wraps a single insertion and deletion (see role="insertion" and role="deletion" above). role="suggestion" - semantically denotes a single proposed change to an editable document.This is semantically equivalent to the HTML element. role="mark" - semantically denotes HTML elements containing text that is marked/highlighted for reference purposes. Note that these aren't part of the new ARIA annotations features, but they are of central relevance. These are semantically equivalent to the HTML and elements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |