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

Move accessibility concerns on datalist to a more prominent position #28189

Closed
wants to merge 1 commit into from

Conversation

hkolbeck
Copy link

@hkolbeck hkolbeck commented Jul 26, 2023

This is a major set of accessibility concerns, and right now it's below the tech specs. This needs to be somewhere people will notice it.

Description

Right now the accessibility concerns on are buried in a place they won't be noticed, given their severity it seems worth putting this somewhere more prominent

Motivation

I care about web accessibility, and I want other folks to be alerted when they're making the web less accessible.

This is a major set of accessibility concerns, and right now it's below the tech specs. This needs to be somewhere people will see it.
@hkolbeck hkolbeck requested a review from a team as a code owner July 26, 2023 06:39
@hkolbeck hkolbeck requested review from chrisdavidmills and removed request for a team July 26, 2023 06:39
@github-actions github-actions bot added the Content:HTML Hypertext Markup Language docs label Jul 26, 2023
@estelle
Copy link
Member

estelle commented Jul 26, 2023

The order of all MDN pages should be approximately the same. That is why the a11y section was located just above specifications

@github-actions
Copy link
Contributor

Preview URLs

@hkolbeck
Copy link
Author

hkolbeck commented Jul 26, 2023

The order of all MDN pages should be approximately the same. That is why the a11y section was located just above specifications

That seems like it's worth a larger conversation. People rarely sit and read through a document like this, burying accessibility somewhere it won't be noticed seems contrary to MDN's ethos.

@bsmth
Copy link
Member

bsmth commented Jul 26, 2023

Hi @hkolbeck thanks for proposing the changes, as Estelle mentioned we're trying to stick to conventions for the page structures. The page template for HTML elements is here: https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Page_structures/Page_types/HTML_element_page_template#accessibility_concerns which at least shows that it can be moved before the technical summary.

That seems like it's worth a larger conversation.

You're more than welcome to start one, we're using GitHub discussions for topics like this if you feel like opening one.

Thanks :)

@hkolbeck
Copy link
Author

I've started a discussion here: https://github.com/orgs/mdn/discussions/430

@chrisdavidmills
Copy link
Contributor

I'm down to review this, but I think we should resolve the discussion first. I've gone over there and given my 2 cents.

@estelle
Copy link
Member

estelle commented Jul 29, 2023

Not sure what the final decision will be, but this is likely not going to be it. Closing. If we decide to go with this, we can re-open

@estelle estelle closed this Jul 29, 2023
@hkolbeck hkolbeck deleted the patch-1 branch July 29, 2023 00:18
@hkolbeck
Copy link
Author

Absolutely, I meant to close this. Apologies.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Content:HTML Hypertext Markup Language docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants