[xwiki-devs] [VOTE] Introduce new "accessibility" CSS class for skins
Hi, While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box). Another example are "skip content" and "got to top" features. Thus I'd like to propose adding a new public CSS class called "accessibility": .accessibility { display: none } We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed). WDYT? Here's my +1 Thanks -Vincent PS: BTW this raises the question of public vs non public CSS classes. Do we have a list somewhere? If not shouldn't we have one to let skin authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
On 11/12/09 5:13 PM, Vincent Massol wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
+1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes. Do we have a list somewhere? If not shouldn't we have one to let skin authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
+1 Some classes (like "hidden") disappeared with colibri, thus "breaking" the layout of apps that relied on it, so yes we should list what is "API" and what is internal. Jerome.
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Thu, Nov 12, 2009 at 17:13, Vincent Massol <[email protected]> wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes. Do we have a list somewhere? If not shouldn't we have one to let skin authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
+1 we should have a documented list of the required classes and what us expected from theses classes
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Thu, Nov 12, 2009 at 17:26, Thomas Mortagne <[email protected]>wrote:
On Thu, Nov 12, 2009 at 17:13, Vincent Massol <[email protected]> wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes.
what do you mean? In the cleanup http://incubator.myxwiki.org/xwiki/bin/download/Skins/ColibriClean/colibri.c... there is a list of general elements, like: .clearfloats, .hidden, .invisible, .loading, .separator but classes that absolutely needs to exists are so many :) there are a few classes (I think I saw one once) that are used by a skin and not used by another, but in rest, because toucan was build on top of albatross and colibri on top of toucan, they share mostly the same classes. Jerome - .clearfloats exists in colibri.css :) thank you
Do we have a list somewhere? If not shouldn't we have one to let skin
authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
+1 we should have a documented list of the required classes and what us expected from theses classes
On 11/12/09 5:35 PM, Ecaterina Valica wrote:
On Thu, Nov 12, 2009 at 17:26, Thomas Mortagne<[email protected]>wrote:
On Thu, Nov 12, 2009 at 17:13, Vincent Massol<[email protected]> wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes.
what do you mean? In the cleanup http://incubator.myxwiki.org/xwiki/bin/download/Skins/ColibriClean/colibri.c...
there is a list of general elements, like: .clearfloats, .hidden, .invisible, .loading, .separator but classes that absolutely needs to exists are so many :)
there are a few classes (I think I saw one once) that are used by a skin and not used by another, but in rest, because toucan was build on top of albatross and colibri on top of toucan, they share mostly the same classes.
Jerome - .clearfloats exists in colibri.css :) thank you
Then I don't recall what it was. Anyway, the private (internal) vs API (public) list of classes would allow to separate CSS classes in 2 categories : - the ones with an agreed behavior that all skins must define, and that application (extensions, etc.) developers can rely on. (like we do with hidden, buttonswrapper, clearfloats, etc.) -> those are APIs - the ones that are used to "make the skin work" and for which we allow ourselves to change their behavior, remove them, not define them in all skins, etc. -> those are private, and the extension developers must not rely on them. That's similar to public API vs. private implementation for Java components. Jerome.
Do we have a list somewhere? If not shouldn't we have one to let skin
authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
+1 we should have a documented list of the required classes and what us expected from theses classes
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
although we have a class called .hidden - it was until now used to hide: - accessibility elements, like action menu indicators - JS toggled elements We could have a separation for accessibility elements from the other layout/implementation hidden elements. This could be useful in case we want to transit some accessibility into the layout. or we could keep .hidden to do both. Jerome, .hidden did NOT disappeared from colibri.css. On Thu, Nov 12, 2009 at 17:13, Vincent Massol <[email protected]> wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes. Do we have a list somewhere? If not shouldn't we have one to let skin authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 11/12/09 5:27 PM, Ecaterina Valica wrote:
although we have a class called .hidden - it was until now used to hide: - accessibility elements, like action menu indicators - JS toggled elements
We could have a separation for accessibility elements from the other layout/implementation hidden elements. This could be useful in case we want to transit some accessibility into the layout.
or we could keep .hidden to do both.
Jerome, .hidden did NOT disappeared from colibri.css.
My bad, the class I had in mind was .clearfloats, not .hidden Jerome.
On Thu, Nov 12, 2009 at 17:13, Vincent Massol<[email protected]> wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes. Do we have a list somewhere? If not shouldn't we have one to let skin authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
ok I wasn't aware of the .hidden class. So do we still want a new .accessibility class or should we use the .hidden one? My take is that .accessibility is more semantic (which means we don't need to add a comment wherever we use it for accessibiility reasons) but OTOH it introduces a new class. I'm still +1 to add it. Thanks -Vincent On Nov 12, 2009, at 5:27 PM, Ecaterina Valica wrote:
although we have a class called .hidden - it was until now used to hide: - accessibility elements, like action menu indicators - JS toggled elements
We could have a separation for accessibility elements from the other layout/implementation hidden elements. This could be useful in case we want to transit some accessibility into the layout.
or we could keep .hidden to do both.
Jerome, .hidden did NOT disappeared from colibri.css.
On Thu, Nov 12, 2009 at 17:13, Vincent Massol <[email protected]> wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes. Do we have a list somewhere? If not shouldn't we have one to let skin authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Nov 13, 2009, at 11:00 AM, Vincent Massol wrote:
ok I wasn't aware of the .hidden class.
So do we still want a new .accessibility class or should we use the .hidden one?
My take is that .accessibility is more semantic (which means we don't need to add a comment wherever we use it for accessibiility reasons) but OTOH it introduces a new class.
I'm still +1 to add it.
Sergiu isn't sure about .accessibility since there are existing accessibility stuff already so I'll commit with .hidden for now till we agree on how we want to manager accessbiility stuff in general. Please let's continue this discussion. Waiting for Sergiu's proposal :) Thanks -Vincent
Thanks -Vincent
On Nov 12, 2009, at 5:27 PM, Ecaterina Valica wrote:
although we have a class called .hidden - it was until now used to hide: - accessibility elements, like action menu indicators - JS toggled elements
We could have a separation for accessibility elements from the other layout/implementation hidden elements. This could be useful in case we want to transit some accessibility into the layout.
or we could keep .hidden to do both.
Jerome, .hidden did NOT disappeared from colibri.css.
On Thu, Nov 12, 2009 at 17:13, Vincent Massol <[email protected]> wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes. Do we have a list somewhere? If not shouldn't we have one to let skin authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
On Thu, Nov 12, 2009 at 5:13 PM, Vincent Massol <[email protected]> wrote:
Hi,
While working on WCAG we've found that we need to hide some content so that it's not displayed visually but it's used by assistive devices (such as a web browser reader). For example for label texts in compact forms (where we put the label inside the field -e.g. the search box).
Another example are "skip content" and "got to top" features.
Thus I'd like to propose adding a new public CSS class called "accessibility":
.accessibility { display: none }
We need a vote since it's public and would be used for example in the form located in Main.Spaces. This means that all skins (ours or custom skins done by users) must have it (or the label will be displayed).
WDYT?
Here's my +1
+1
Thanks -Vincent
PS: BTW this raises the question of public vs non public CSS classes. Do we have a list somewhere? If not shouldn't we have one to let skin authors know what class must absolutely exist and also to ensure we don't use non public classes in document content or in templates (non skin templates)?
+1 to start to build such a list, AFAIK we don't have one FTM. http://platform.xwiki.org/xwiki/bin/view/DevGuide/FrontendResources JV.
participants (5)
-
Ecaterina Valica -
Jean-Vincent Drean -
Jerome Velociter -
Thomas Mortagne -
Vincent Massol