A huge problem with almost every CMS in existence is the extremely poor quality of the code produced by their WYSIWYG editors.
Group items matching
in title, tags, annotations or urlTerrill Thompson - 0 views
Forget WYSIWYG editors - use WYSIWYM instead | 456 Berea Street - 0 views
-
-
Since visual gadgetry like WYSIWYG editors sells, every CMS has to have one.
-
That, in turn, makes it necessary for Web professionals who want to reduce the risk of clients unknowingly ruining the website’s semantics and accessibility to disable features and implement more or less advanced code cleaning procedures. It is a mess.
- ...4 more annotations...
Prettier Accessible Forms · An A List Apart Article - 0 views
-
The fieldset element allows us to group form controls into logical, related “chunks.” legend then allows us to add a caption to that fieldset, which helps users understand the context of the form controls contained within that fieldset. In some screen readers, the legend is associated with each form control within a fieldset and is read out after each tab of the keyboard, so that a particular control can always be referenced back to its legend.
-
Breadcrumbs: 11 Design Guidelines for Desktop and Mobile - 0 views
-
the breadcrumb corresponding to the current page should not be a link. You should never have a link that does nothing. The last breadcrumb (denoting the current page) should not be a link.
-
The breadcrumb denoting the current page SHOULD be a link and differentiated from others via mechanisms such as aria-current="page" See https://scottaohara.github.io/a11y_breadcrumbs/ for this pattern.
-
The breadcrumb denoting the current page SHOULD be a link and differentiated from others via mechanisms such as aria-current="page" See https://scottaohara.github.io/a11y_breadcrumbs/ for this pattern.
-
-
Include the current page as the last item in the breadcrumb trail.
-
Breadcrumb trails should start with a link to the homepage.
- ...14 more annotations...
-
‹ Previous
21 - 28 of 28
Showing 20▼ items per page