From b25b56137e3b31b6e4e745a6b5e79843e46a9a98 Mon Sep 17 00:00:00 2001 From: Eric Bidelman Date: Mon, 17 Nov 2014 17:17:33 -0800 Subject: [PATCH] Removing navgroup cruft --- _layouts/default.html | 2 +- articles/accessible-web-components.md | 25 ++++--- articles/communication.md | 15 ++--- articles/concatenating-web-components.md | 13 ++-- .../distributing-components-with-bower.md | 15 ++--- articles/index.md | 3 +- articles/polymer-xtag-vanilla.md | 3 +- articles/spa.md | 3 +- articles/styling-elements.md | 29 ++++---- articles/unit-testing-elements.md | 13 ++-- build/index.md | 3 +- css/elements/docs-menu.css | 2 +- css/homepage.css | 2 +- css/site2.css | 2 +- discuss.md | 3 +- docs/elements/core-elements.md | 1 - docs/elements/icons.md | 23 +++---- docs/elements/layout-elements.md | 1 - docs/elements/material.md | 55 ++++++++------- docs/elements/paper-elements.md | 3 +- docs/polymer/binding-types.md | 7 +- docs/polymer/databinding-advanced.md | 47 +++++++------ docs/polymer/databinding-compat.md | 13 ++-- docs/polymer/databinding.md | 67 +++++++++---------- docs/polymer/debugging.md | 57 ++++++++-------- docs/polymer/expressions.md | 3 +- docs/polymer/filters.md | 3 +- docs/polymer/helpers.md | 27 ++++---- docs/polymer/layout-attrs.md | 11 ++- docs/polymer/node_bind.md | 5 +- docs/polymer/polymer.md | 51 +++++++------- docs/polymer/runtime-config.md | 5 +- docs/polymer/styling.md | 3 +- docs/polymer/template.md | 7 +- docs/polymer/touch.md | 3 +- docs/start/creatingelements.md | 1 - docs/start/customelements.md | 5 +- docs/start/everything.md | 5 +- docs/start/getting-the-code.md | 1 - docs/start/platform.md | 3 +- docs/start/reusableelements.md | 41 ++++++------ docs/start/tutorial/intro.md | 13 ++-- docs/start/tutorial/step-1.md | 65 +++++++++--------- docs/start/tutorial/step-3.md | 27 ++++---- docs/start/tutorial/step-4.md | 31 +++++---- docs/start/usingelements.md | 1 - js/app.js | 6 +- platform/custom-elements.md | 5 +- platform/html-imports.md | 3 +- platform/mutation-observers.md | 5 +- platform/pointer-events.md | 5 +- platform/shadow-dom.md | 3 +- platform/web-animations.md | 5 +- resources/changelog.md | 11 ++- resources/compatibility.md | 3 +- resources/faq.md | 7 +- resources/tooling-strategy.md | 13 ++-- resources/video.md | 3 +- sass/elements/docs-menu.scss | 21 ++++-- sass/elements/site-banner.scss | 12 ---- sass/site2.scss | 18 +---- 61 files changed, 388 insertions(+), 450 deletions(-) diff --git a/_layouts/default.html b/_layouts/default.html index ae864b2c78..716e478fce 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -22,7 +22,7 @@ - + {% include top-nav.html %}

{{page.title}}

diff --git a/articles/accessible-web-components.md b/articles/accessible-web-components.md index e9a877798e..1c99a5a646 100644 --- a/articles/accessible-web-components.md +++ b/articles/accessible-web-components.md @@ -1,7 +1,6 @@ --- layout: default -type: core -navgroup: docs +type: guide shortname: Articles title: "Accessible Web Components - Part 1" subtitle: Improving the accessibility of Web Components @@ -39,21 +38,21 @@ When designing for accessibility, there are four key areas of disability to cons * Ensure all user interface elements can be used with assistive technologies such as screen readers, magnifiers and braille displays. This entails ensuring that elements are marked up such that accessibility APIs can programmatically determine the *role*, *state*, *value* and *title* of any element. -**Hearing** issues mean a user may have issues hearing sound emitted from a page. +**Hearing** issues mean a user may have issues hearing sound emitted from a page. -* Make the content understandable using [text alternatives](http://www.w3.org/TR/WCAG20/#media-equiv-av-only-alt) for all content that is not strictly text. +* Make the content understandable using [text alternatives](http://www.w3.org/TR/WCAG20/#media-equiv-av-only-alt) for all content that is not strictly text. * Ensure you test that your elements are still functional [without sound](http://www.w3.org/TR/2008/REC-WCAG20-20081211/#content-structure-separation-understanding). -**Mobility** issues can include the inability to operate a mouse, a keyboard or touch-screen. +**Mobility** issues can include the inability to operate a mouse, a keyboard or touch-screen. * Make the content of your elements [functionally accessible from a keyboard](http://www.w3.org/TR/wai-aria-practices/#keyboard) for any actions one would otherwise use a mouse for. * Ensure user interface elements are correctly marked up for assistive technologies; these users may use technologies such as voice control software and physical switch controls, which tend to use the same APIs as other assistive technologies like screen readers. -**Cognitive** issues mean a user may require assistive technologies to help them with reading text, so it’s important to ensure text alternatives exist. +**Cognitive** issues mean a user may require assistive technologies to help them with reading text, so it’s important to ensure text alternatives exist. -* Avoid a visual presentation that is [repetitive](http://www.w3.org/TR/WCAG20/#time-limits) or flashing as this can cause some users [issues](http://www.w3.org/TR/WCAG20/#seizure). +* Avoid a visual presentation that is [repetitive](http://www.w3.org/TR/WCAG20/#time-limits) or flashing as this can cause some users [issues](http://www.w3.org/TR/WCAG20/#seizure). * Avoid interactions that are timing-based. @@ -79,13 +78,13 @@ Native controls (such as `