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

Documenting the project's browser support requirements #2644

Closed
jugglinmike opened this issue Mar 15, 2023 · 3 comments
Closed

Documenting the project's browser support requirements #2644

jugglinmike opened this issue Mar 15, 2023 · 3 comments
Assignees

Comments

@jugglinmike
Copy link
Contributor

For folks who want to contribute to the APG example code, it's currently unclear which web platform features are "safe" to use. This is because the project does not document the browsers in which the examples must operate.

This is currently a problem for me because I'm wondering whether the APG examples can be refactored to use import declarations, but a policy here will generally reduce uncertainty for contributors and reviewers.

@w3c/aria-practices Would you mind sharing your expectations about which browsers (and at which versions) the examples must support?

@mcking65
Copy link
Contributor

This does not resolve this issue, but it is worth noting that in the read this first, under browser support, it says:

Similarly, JavaScript and CSS in this guide is written to be compatible with the most recent version of Chrome, Firefox, and Safari at the time of writing. Some JavaScript and CSS may not function correctly in Internet Explorer.

@css-meeting-bot
Copy link
Member

The ARIA Authoring Practices (APG) Task Force just discussed APG browser support requirements.

The full IRC log of that discussion <jugglinmike> Topic: APG browser support requirements
<jugglinmike> github: https://github.com//issues/2644
<jugglinmike> Matt_King: Just prior to this meeting, I added a comment about the policy
<jugglinmike> Matt_King: But we should probably add something about this to the project's contribution guidelines
<jugglinmike> jamesn: I don't think people care about old versions of browsers anymore because everything auto-updates
<jugglinmike> Matt_King: I think this is most important for folks who are in enterprise environments where browsers don't update as often
<jugglinmike> Matt_King: I wonder if we should remove even the reference to Internet Explorer in the text since that tends to make it feel dated
<Jem> jugglinmike: I will document this in the code guidance and update the apg doc regarding IE mention.
<jugglinmike> Matt_King: We don't have to worry about enterprise as an audience for APG itself. It's enough to warn readers about the support considerations in their own projects (and the text already does include such a warning)

@jugglinmike
Copy link
Contributor Author

We have resolved this with the following changes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants