-
-
Notifications
You must be signed in to change notification settings - Fork 514
Adjustments to A11y Lang Attribute section #1467
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
Conversation
|
||
Note: a page cannot have multiple language attribute _values_. For example, this means that `lang="en"` could be set on the page's HTML element and then `lang="es"` could be set on a different element in the page content (as appropriate). | ||
The `html` element may not have multiple `lang` _values_. Instead, an element containing content in a different language than the `html`'s `lang` may be wrapped in an element with its own `lang` attribute. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 2nd sentence felt a little awkward. Does the following convey your meaning well?
The `html` element may not have multiple `lang` _values_. Instead, an element containing content in a different language than the `html`'s `lang` may be wrapped in an element with its own `lang` attribute. | |
The `html` element may not have multiple `lang` _values_. If an element contains content in a language different from the primary, then you can provide the element its own `lang` attribute. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The updated passages looked good overall. I left a few suggestions in the release
version, but each suggestion would apply to all version starting with v3.12.0
(which, I think, is missing in this PR?).
I'd like to request 4 changes:
- Make changes to
v3.12.0
as well (unless there was a reason not to). - Include the words
ember-intl
andlang
as lint exceptions in the file.local.dic
. Doing so should help Travis CI pass. - I think we should avoid the reference to
ember new --lang
until the feature is implemented. - I think we should avoid style changes in this PR. If you run
git grep -n "^> "
in theguides/release
folder, you will see that the<blockquote>
element is used in several places. I do think the current style for<blockquote>
isn't great. Updating the style would be better done in a separate PR (I'd open an issue first to invite feedback from general public) and invite @MelSumner and @mansona to provide feedback on what's the best way to update style for Ember Guides.
Can you rebase from the upstream master
once more? Percy's "before" snapshots are using an old reference.
f9dfc11
to
27b0fa2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this PR. It looks great!
* Text content rewrite of a11y lang attr * Illustration for sub elements with dif lang * Ported to v3.13-v3.17 * Ported to v3.18 * Applied PR feedback Co-authored-by: Ava Wroten <[email protected]>
Adjusts some copy based on what we've learned during the ember new lang RFC, clarifies some points, adds some reference links, adds a zoey says section and a visual illustration to better explain where the attribute goes.
Styled blockquotes, seems it hasn't been done before? So I just went for it trying to give it a generic but reusable style that seems to match the guides.
Rendered:
