Accessibility questionnaire

[xfq]

https://w3c.github.io/apa/fast/checklist.html

If technology allows visual rendering of content

[✔️] There is a defined way for a non-visual rendering to be created.

It is possible to create a string representing the accessible name of every image resource (icons' label attribute).

[ ] Content can be resized.

The icons can not be resized, but the icons member specifies an array of objects representing image files that can serve as application icons for different contexts. These icons may have different sizes associated (e.g., sizes: "16x16 32x32 64x64")

[ ] Luminosity and hue contrast can adapt to user requirements.

There is currently no way to do this via the manifest. MiniApp developers/authors can develop this feature themselves.

[ ] Text presentation attributes can be changed.

There is currently no way to customize the string representing the accessible name of image resources.

[✔️] Changing content presentation does not render it unreadable.

[✔️] Technology does not allow blinking or flashing of content, or provides a feature for users to quickly turn it off or permanently disable it.

[✔️] It is possible to make navigation order correspond to the visual presentation.

It seems not to be applicable to the MiniApp Manifest.

If technology provides author control over color

[ ] There is a mechanism for users to override colors of text and user interface components.

User agents may provide such mechanism, but this is outside the scope of this spec.

[✔️] There is a feature for authors to define semantically available "color classes" that users can easily map to custom colors, and give preference to this vs. coloring objects individually.

[✔️] There is a feature for users to choose color schemata that work for them.

[✔️] The foreground and background color of an object can be reported to the user via AT.

I'm not familiar with AT, but from what I understand it's technically possible.

[✔️] There are ways to set foreground and background colors separately for all objects.

[✔️] Compositing rules for foreground and background colors are well defined.

If technology provides features to accept user input

This specification does not provide features to accept user input.

If technology provides user interaction features

This specification does not provide user interaction features.

If technology defines document semantics

This specification does not define document semantics.

If technology provides time-based visual media

This specification does not provide time-based visual media.

If technology provides audio

This specification does not provide audio.

If technology allows time limits

This specification does not allow time limits.

If technology creates objects that don't have an inherent text representation

This specification does not create objects that don't have an inherent text representation.

If technology provides content fallback mechanisms, whether text or other formats

This specification does not provide content fallback mechanisms, whether text or other formats.

If technology provides visual graphics

This specification itself does not provide visual graphics.

If technology provides internationalization support

[✔️] Accessibility features can be internationalized to the same degree as other features.

If technology defines accessible alternative features

[ ] Accessible alternatives themselves meet the same bar of accessibility.

Text alternatives to image resources do not allow rich content, but it is defined in a separate spec.

If technology provides content directly for end-users

[✔️] Content can be encoded in a manner that allows machine transformation into accessible output.

If technology defines an API

This specification does not define an API.

If technology defines a transmission protocol

This specification does not define a transmission protocol.

[xfq]

@espinr PTAL! This is part of the process of asking for an accessibility review for this specification. Feel free to edit the first comment with more info if needed. Once we're happy with the result we can add the a11y-tracker label to start the a11y review.

[espinr]

Thanks @xfq . It looks good to me. Only a few additions to your comments