-
Notifications
You must be signed in to change notification settings - Fork 126
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
editorial: revise custom stylesheets #2410
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for wai-aria ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
notes to self:
|
It turns out, core-aam only sets styling that are already set in common.css. |
@jnurthen @spectranaut @daniel-montalvo I think I actually want to suggest to remove all of common.css. Almost all of it is minor stylistic differences to what respec does (i.e., everything after the table styles). For tables, I would suggest to switch to respec's The only other bit are the nested lists styles. However, only accname actually needs these (and I feel like respec or W3C TR styles should be doing a better job here - but they probably don't want to risk it but perhaps be open to opt-in classes). [For completeness: there are 2 nested lists in aria in 4.3.2 - all other nested lists in specs are from respec TOCs where the styles are set by respec.] I'll prep something for the next editors meeting so we can go through them together. |
Discussed in editors' call https://www.w3.org/2025/01/22-aria-editors-minutes.html#1b79 tl;dr I will continue this PR to effectively remove common.css |
@jnurthen looking through https://w3c.github.io/tr-design/src/README I see 1-2 other table styles: Are there others you had in mind? |
I think I was thinking about the default style without data for some of the tables at the end of the doc |
Removes styles that match 1 list in aria, accname, core-aam, pdf-aam; only 1 minor visual change in accname, otherwise margin-collapse helps. Part of #2410
All props are overruled by respec. Part of #2410
As per editors discussion, we switch to the default respec style. Part of #2410
As per editors discussion, we switch to the default respec style. Part of #2410
As per editors discussion, we switch to default respec / highlightjs styles. Part of #2410
As per editors discussion, we remove the nested list and add a style block with custom classes to accname. - common.css: remove nested OL styles - accname/index.html - add style block with custom classes - add appropriate classes to nested lists in 4.3.2 (except in the first note and example 3) Part of #2410
As per editors discussion, removes common.css and adds respec classes to tables. - switches existing classes to .def - adds .def to IDL correspondance table - switches 2 classless tables to "data" Part of #2410
This file no longer appears to be used anywhere. Part of #2410
This file no longer appears to be used anywhere. Part of #2410
As per today's call, I will switch the other specs to using respec table classes. Then the editors can review each spec. @MelSumner could you take a look at the nested list classes I've added to accname 42082b0? @spectranaut suggested it might be better to design the lists in a way so that new nested lists can be added without having to remember the right class. It seems prudent to ask a spec editor to do that 😄 |
As per editors discussion, we remove the nested list and add a style block with custom classes to accname. - common.css: remove nested OL styles - accname/index.html - add style block with custom classes - add appropriate classes to nested lists in 4.3.2 (except in the first note and example 3) Part of #2410
As per editors discussion, removes common.css and adds respec classes to tables. - switches existing classes to .def - adds .def to IDL correspondance table - switches 2 classless tables to "data" Part of #2410
This file no longer appears to be used anywhere. Part of #2410
This file no longer appears to be used anywhere. Part of #2410
Removes common.css and adds respec class "data" to the table (in "4.2 Description Computation"). Part of #2410
As per editors discussion, removes common.css and replaces .role-features with respec's .def Part of #2410
As per editors discussion, removes common.css and replaces .role-features with respec's .def Part of #2410
Removes common.css and mapping-tables.css and adds respec's .data to all tables Part of #2410
Removes common.css and mapping-tables.css and adds respec's .data to all tables Part of #2410
Removes common.css and mapping-tables.css and adds respec's .data to all tables Part of #2410
Removes common.css and mapping-tables.css and adds respec's .data to all tables Part of #2410
Removes common.css and mapping-tables.css and adds respec's .data to all tables Part of #2410
Removes common.css and mapping-tables.css and adds respec's .data to all tables Part of #2410
Removes common.css and mapping-tables.css and adds respec's .data to all tables Part of #2410
As per editors discussion, removes common.css and replaces table classes with respec's .def Part of #2410
At long last, it is longer in use. Part of #2410
At long last, it is longer in use. Part of #2410
This is ready for review. While rebasing I fixed a typo in html-aam (extraneous closing parenthesis in the img alt section). |
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.
I have one request about the CSS for nested lists, I'd like @MelSumner to weigh in as she is the visual editor of that spec :)
Also -- I think we should have, perhaps a follow up issue, to make all the data tables in the aams use class=def
to get the blue definition tables: https://www.w3.org/StyleSheets/TR/2021/README#def
<style> | ||
.ol--upperAlpha{ list-style:upper-alpha; } /* replaces: ol ol */ | ||
.ol--lowerRoman { list-style:lower-roman; } /* replaces: ol ol ol */ | ||
.ol--lowerAlpha { list-style:lower-alpha; } /* replaces: ol ol ol ol */ |
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.
Can't we do something like putting the class "computation_algorithm" on the rool ol
and then do:
.computation_algorithm ol ol { list-style:upper-alpha; }
.computation_algorithm ol ol ol { list-style:lower-roman; }
.computation_algorithm ol ol ol ol {l ist-style:lower-alpha; }
And remove those custom classes on the nest ol
s, so no one has to worry about adding then when they make a nested list in a computation?
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.
Two minor notes:
- if
.computation_algorithm
goes on an OL, this needs to drop one ol from each line. - then these styles would still affect the two lists in the Note and Example
As I said on the call, I have no strong feelings either way. But we can also work this out later. (I'm a little worried about merge conflicts as I'm touching all the specs.)
@spectranaut ugh, sorry, that's my fault. I misread #2229 and thought you wanted the I'll update the PR tomorrow. |
Done. |
Resolves #2226
th{ background-color:#eee; }
(cf. Text-to-background contrast in tables under ARIA's Definition of Roles too low #2394 + duplicates)#example-48
=> https://github.com/speced/respec/wiki/ReSpec-Editor's-Guide#examples => follow up to css revision #2433.data
as per review mapping-tables.css #2435 , Move all AAM specs to use w3c's "data tables" #2229 [cf. notes above]Preview | Diff