Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[COGA] 2.6.6 Using Multimodal Interfaces to Enhance Understanding #2

Open
RealJoshue108 opened this issue Jan 10, 2022 · 9 comments
Open
Assignees

Comments

@RealJoshue108
Copy link
Contributor

[Added on behalf of COGA TF]

  • Note after User Need 26: Consider broadening the wording, as noted here in brackets: “The purpose of this multimodal presentation of text is to enhance comprehension of the material, especially by people with [replace “learning disabilities that affect reading” with “reading disabilities”].”
  • Additional REQ for User Need 27: Consider adding an REQ about icons. Familiar icons can help users with cognitive and learning disabilities such as ADHD, but unfamiliar icons can be confusing/distracting.
  • Note after User Need 27: Add sentence, as noted here in brackets: “Information presented graphically must also be available as text. See '§ 2.2 Means of Input and Output' above. [Add: Ensure the system does not read out text that would be redundant information for those using text only.]”
@RealJoshue108 RealJoshue108 self-assigned this Jan 10, 2022
@RealJoshue108
Copy link
Contributor Author

RealJoshue108 commented Jan 19, 2022

Notes additional suggested requirement for user need 27 - Familiar icons can help users with cognitive and learning disabilities such as ADHD

@RealJoshue108
Copy link
Contributor Author

Discussed in RQTF, and happy to make editorial change for item one:

Note after User Need 26: Consider broadening the wording, as noted here in brackets: “The purpose of this multimodal presentation of text is to enhance comprehension of the material, especially by people with [replace “learning disabilities that affect reading” with “reading disabilities”].”

@RealJoshue108
Copy link
Contributor Author

@JaninaSajka thinks we need to wait for the Personalization spec to come out to cover the suggested new REQ for 27.

Additional REQ for User Need 27: Consider adding an REQ about icons. Familiar icons can help users with cognitive and learning disabilities such as ADHD, but unfamiliar icons can be confusing/distracting.

@RealJoshue108
Copy link
Contributor Author

+1 from me on waiting for Personalisation Spec to cover some fo these AAC type requirements.

@RealJoshue108
Copy link
Contributor Author

@JaninaSajka we can discuss this further however, there are brand related issues but pushback on the use of the word 'familiar'.

@RealJoshue108
Copy link
Contributor Author

Last point needs clarification - ''Note after User Need 27: Add sentence, as noted here in brackets: “Information presented graphically must also be available as text. See '§ 2.2 Means of Input and Output' above. [Add: Ensure the system does not read out text that would be redundant information for those using text only.]”"

@RealJoshue108
Copy link
Contributor Author

Discussed by Research Questions Task force https://www.w3.org/2022/01/19-rqtf-minutes.html

@RealJoshue108
Copy link
Contributor Author

RealJoshue108 commented Jan 25, 2022

Similar personalization request that relates to #8

@RealJoshue108
Copy link
Contributor Author

Discussed in Research Questions Task Force 26th Jan 2022 https://www.w3.org/2022/01/26-rqtf-minutes.html

@ruoxiran ruoxiran transferred this issue from w3c/apa Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant