zulooflowers.blogg.se - Standard notes themes

STANDARD NOTES THEMES HOW TO
STANDARD NOTES THEMES UPDATE

That feature wasn't consistently supported by Chrome. It was an experimental feature that was removed from an old CSS W3C editor draft.

Currently that feature is only limited to webkit browser and FF by applying some prefix vendor. It is explicitly said that anti-aliasing CSS is not in a standard track and it is recommended to avoid.

Special notes Use of font smoothing anti-aliasing RequirementĬonfigure the font smoothing anti-aliasing CSS for GCWeb theme v5. From that test, the recommendation was to replace the button text "top menu" by "main menu".

October 22-26, 2018: Partial screen reader compatibility test has been made to the new menu, but for a different markup compared to the one published as Oct 31.

November 14, 2018: 1 - Accessibility assesment of GCWeb theme version 2.

November 16, 2018: 2 - Regression user acceptance testing of WET plugin for GCWeb theme version 2.

February 20, 2019: Test on the menu component (French only).

WAI-ARIA Practices 1.1 - Action Menu button using element.focus().

WAI-ARIA Practices 1.1 - Editor Menubar Example.

WAI-ARIA Practices 1.1 - 3.14 Menu or Menu bar.

WAI-ARIA Practices 1.1 - 3.15 Menu Button.

The menu item focus are managed by using a Roving tabindex.

Also the DOM markup should validate after any DOM manipulation that are happing in the page) the value true is equivalent to setting the value menu - (Note the validation, as per WCAG 2.0 and WCAG 2.1 should be done after all JS has run and the DOM is mark "ready". But in order to pass the whatwg validation, when the markup are validated as output by the server, as a best practice because w3c, the value of aria-haspopup was change to true.

Originally the attribute aria-haspopup was set with the value menu.

The double role on list item in the menu was added as suggested by the W3C validator because the role=none are not widely supported yet.

The menu was designed similary like the menu design pattern from WAI-ARIA 1.1.

Here a working example: Content page - GCWeb 4.0.29 font style Reference and notes

Content inside a container with the CSS class force-style-gcweb-4-0-29.

Button (exception of the new call to action button).

For example a datatable with 10 columns or more in a report.

Pages where datatables was intentionally skrinked in order to fit all columns inside the extra-large view port (desktop).

STANDARD NOTES THEMES HOW TO

Those cases might require you to re-think how to present the information. Textual content inside a column of width of 3 might or might not cause issue. Pages where there is textual content inside a column of a width of 1 and 2.Pages where the number of characted (like in a title) are closely counted to ensure it fit in a specific container, like to remain in one single line.Mostly the one where it was thighly designed for desktop first, like some campaign pages. The increased font size and the new line-height might impact some visual design. Header: White background replaces light grey.Search box: Larger, white background replaces grey, closer to menu.Breadcrumbs: arrow replaced with chevron.This is a list of perceptible changes that would be visually noticiable if only the GCWeb javascript and CSS are replaced without doing any markup change as identified by the migration instruction. Noticable visual difference with no markup change Temporary internal list of issues and todo.See the section bellow Temporary avoiding the visual difference.Demos (Where you can see all the area where a change apply):.Change: How to identify navigation pages (Themes, topics.).Migration instruction (from v4.0.29 to v5).

STANDARD NOTES THEMES UPDATE

The GCWeb v5 (Canada.ca theme) visual update are supporting the Canada.ca Content and Information Architecture Specification 2.0. GCWeb theme - Meta information GCWeb Canada.ca theme) visual update - V5