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

Add Treegrid Example #762

Merged
merged 45 commits into from
Jul 12, 2018
Merged

Add Treegrid Example #762

merged 45 commits into from
Jul 12, 2018

Conversation

mcking65
Copy link
Contributor

@mcking65 mcking65 commented Jul 11, 2018

For issue #132, merging review-ready version of treegrid example developed by @aleventhal and edited to fit example template by @jongund.


Preview | Diff

mcking65 and others added 30 commits April 17, 2017 14:27
1. Modified aria-practices:
    * Add placeholder section for treegrid design pattern.
    * Add link to treegrid example page.
2. Add new template file: examples/treegrid/css/treegrid.css
3. Add nnew template file: examples/treegrid/js/treegrid.js
4. Add new template file:   examples/treegrid/treegrid-1.html
For issue #132, this commit includes:

* Initial implementation of an example treegrid with primarily tree-like behaviors.
* Partial draft of example page content explaining the implementation.
…ells can be focused (pull #369)

For issue #132: If the treegrid is configured so that rows can not be focused, then the first cell controls the expand/collapse behavior. In this case, aria-expanded will be on the first cell in each row instead of on the row.
* Enter on first cell to toggle expansion was not working

* Expando button not showing in ?cell=force mode
More positive email thread about treegrids
Rename from convoluted name to treegrid-1
…n (pull #710)

For issue #132 to develop treegrid example:

* Converted documentation to standard APG template format.
* Filled in documentation gaps.
* Changed treegrid label.
* removed use of aria-hidden.
Copy link
Contributor Author

@mcking65 mcking65 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have some validation issues to resolve. Two are easily fixed. Two require updates to ARIA and the validator (setsize and posinset on rows).

</colgroup>
<thead>
<tr>
<th role="columnheader">Subject</th>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aleventhal, @jongund, why is role columnheader added here. This is not necessary and not recommended to duplicate native semantics. Can we safely remove without breaking any selectors or js?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, a th can be a columnheader or a rowheader. I don't think it's redundant to specify. This way the browser does not need to fall back on heuristics (which different browsers may disagree about).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually we can probably use scope="col".

<thead>
<tr>
<th role="columnheader">Subject</th>
<th role="columnheader">Summary</th>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aleventhal, @jongund, why is role row added here and on subsequent tr elements? This is not necessary and not recommended to duplicate native semantics. Can we safely remove without breaking any selectors or js?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. I would guess that it makes no difference and can be removed, but I think it should be tested with at least one screen reader to be completely sure.

FWIW, I find it easier to understand the examples when the roles are explicitly stated. When we remove "row" from the markup, should we also make sure it's clear in the docs that can be replaced with something like

?

@mcking65
Copy link
Contributor Author

OK ... Editorially in reasonable shape and the only errors left are the posinset and setsize errors, which are being addressed by w3c/aria#558. So, merging to master.

@mcking65 mcking65 merged commit 84fb90f into master Jul 12, 2018
michael-n-cooper pushed a commit that referenced this pull request Jul 13, 2018
For issue #132, adds an example of the treegrid pattern.
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

Successfully merging this pull request may close these issues.

3 participants