github-actions[bot]
commented
4 years ago This Feature Request was accepted, but are not going to be implemented in next release.
Open ecureuill opened 4 years ago
github-actions[bot]
commented
4 years ago This Feature Request was accepted, but are not going to be implemented in next release.
This is a "not-end" requirement. What I want to mean is that this should be considered for any new page you create that Student can access. Also should correct the old pages.
I will use the label Feature Design Notes to this cases
WCAG: 1.3.6
This success criteria requires developers to identify the type and purpose of purpose of icons, regions and components (such as buttons, links, and fields) on the page. The intent is to allow personalization of the content to help people with cognitive disabilities. Assistive technologies could use the additional information about an item to adapt it for the user.
[ ] Add semantics or metadata that provide this context. It is similar to adding role information (as required by 4.2.1) but instead of providing information about what the UI component is (such as an image) it provides information about what the component represents (such as a link to the home page).
[ ] add landmarks #84
[ ] Use aria states and properties
Personalization Semantics vocabulary can be used in HTML content using data- attributes [html5]. Attributes in this form can be used in valid HTML to implement features recognized by browser extensions or other special processors. Personalization Semantics is using this approach to gain early implementation experience of the features in a way that is simple and likely to be accepted within the web ecosystem as an interim approach.
Live-Demo example https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html
some User Stories
[ ] Scenario: personalize components GIVEN I'm a students with special needs WHEN I access a page with my user agent configured to dapt submit buttons THEN,
the the submit button should render with an alternative term and furnish an additional tooltip and be identified with a keyboard shortcut that is always used for submit SO THAT will help me to better understand the page
[ ] Scenario: Augmented and Alternative Communication (AAC) system GIVEN I'm a students who communicate using symbol WHEN I access a page with my user agent configured to use my preferable ACC set THEN, the user interface of the page should a adapt to render using my ACC set SO THAT will help me to better understand the page
[ ] Scenario: Dycalculia GIVEN I'm a students with Dycalculia W HEN I access a page with numeric information and select to adapt it for dyscalculia
THEN, the user interface adapts to use some alternative (as an image, symbol, or as written text) SO THAT will help me to better understand the page
Examples
AAC examples
source
For example, some people use symbols to communicate. They may not understand the icons commonly used on the web. Consider the common icon of a magnifying glass used to indicate a search field
Some users might not understand this symbol and need a customized version. The developer can identify this as a search icon within the code. A custom browser extension or assistive technology could use that information to replace it with the user’s preferred symbol. The search examples below are from the Aragonese Portal of Augmentative and Alternative Communication (ARASAAC) symbol set.
ARASAAC symbols are Copyright arasaac.org and distributed under Creative Commons BY-NC-SA 3.0.
Landmarks example
source
Here is a screenshot of the web page for the Law Office of Lainey Feingold. The dashed purple border marks the header, navigation, main, and complementary regions of the page. The header is at the top. The navigation is underneath the header and flows across the page. The main area is in the left hand side of the page. The complementary section about Lainey’s book is on the right hand side.
The developer has used WAI-ARIA (Web Accessibility Initiative - Accessible Rich Internet Applications) within the code to identify the regions of the page. A software tool could identify and show only the main area to the user. This would cut down distractions and allow the user to concentrate on the content. This becomes more important when a region contains an advertisement or moving content.