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

[RNIB] 4.8 Magnification context and resetting #28

Open
RealJoshue108 opened this issue Apr 6, 2020 · 8 comments
Open

[RNIB] 4.8 Magnification context and resetting #28

RealJoshue108 opened this issue Apr 6, 2020 · 8 comments
Assignees
Labels
enhancement New feature or request XAUR

Comments

@RealJoshue108
Copy link
Contributor

Filed on behalf of RNIB: Original comments sent to APA list

Regarding user need 7 - Alternatively, where it makes sense (such as in menus) interface elements can be enlarged and the menu reflowed. This can make a very usable interface up to a certain magnification requirement.

@RealJoshue108 RealJoshue108 self-assigned this Apr 6, 2020
@RealJoshue108
Copy link
Contributor Author

Do you see this suggestion as new requirement?

Something like:

Req 7.b: Where it makes sense (such as in menus) interface elements can be enlarged and the menu reflowed to enhance the usability of the interface up to a certain magnification requirement.

@RealJoshue108 RealJoshue108 added the enhancement New feature or request label Apr 28, 2020
@Raisonali
Copy link

Yes, I think this works.

@RealJoshue108
Copy link
Contributor Author

@Raisonali This was discussed in RQTF last week. https://www.w3.org/2020/05/20-rqtf-minutes.html

However, we didn't go over my draft requirement text so I will bring this to the group this week. So it would be useful to continue discussing - this may be addressed in Captions and Subtitles etc for XR in Silver.

@RealJoshue108
Copy link
Contributor Author

This could be cross-referenced with WCAG 2.1 Reflow 1.4.10 https://www.w3.org/WAI/WCAG21/Understanding/reflow.html

@RealJoshue108
Copy link
Contributor Author

WCAG 2.1 Reflow is squarely in 2D space - and issues around browser resolutions. This indicates multilayer requirements for Silver.

@RealJoshue108
Copy link
Contributor Author

@Raisonali Discussed again in Research Questions Task Force on 27/5/2020
https://www.w3.org/2020/05/27-rqtf-minutes.html

@matatk
Copy link

matatk commented Jun 10, 2020

Here's an example (originally from w3c/apa#56) of a really great system from academia that can adapt a UI in multiple different ways, e.g.

  • for use on different devices,
  • taking into account different challenges the user may face, such as
    • vision
    • motor control
    • user preferences and abilities, and
  • make multiple adaptations for these different factors at the same time.

Demo and info on SUPPLE:

There are also APIs in both iOS and Android that offer scalable system fonts, but nothing anywhere near as awesome as SUPPLE, so whilst it's great that significant progress is being made, this shows what might be possible :-).

@RealJoshue108
Copy link
Contributor Author

RealJoshue108 commented Jun 29, 2020

Thanks @matatk I've reviewed those SUPPLE videos - it looks like a super interesting project and the idea of automatically generating a UI based on a testing the users ability and preference before building the UI is great. There is for sure room for us to expand on this in our requirements.

@ruoxiran ruoxiran transferred this issue from w3c/apa Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request XAUR
Projects
None yet
Development

No branches or pull requests

3 participants