I don't believe that would work out.
841 karma · joined August 14, 2014
I don't believe that would work out.
* I think everything regarding the `aside` elements has already been said in the GitHub issue: It's context specific and you can't determine in advance if a certain (card) element is part of the main content or not. Therefore, `aside` should only be used if needed. (The top three cards on the MVP.css homepage definitely are part of the main content for example.)
* Your `a i` and `a strong` solutions are pretty unusual and they show the limit of what is possible using a classless CSS. I would have preferred staying even more minimalist and simply pass on button-like links.
* You could think about adding the underlining for links in continuous text. See https://www.w3.org/TR/WCAG20-TECHS/F73.html.
I'm not trying to be a dick about it since it's your personal project and I am not forced to use it – but I am not sure why the framework had to be classless and usable for a MVP all at once. I absolutely love classless CSS for simple/personal websites, but I associate MVPs (products) and rapid prototyping with more extensive and interactive interfaces than the typical text-based onepager.
While it is true that HTML semantics aren't as stringent as often assumed, there certainly are more or less universally accepted best practices. They depend on the complexity of the site itself. (It may also be unclear what a "page header" actually is. It could contain your logo and navigation, but the `<h1>` should rather be in the `<main>` element.)
So this is what my most basic structure inside the `<body>` would look like:
<header></header>
<main></main>
<footer></footer>
If you're doing this with the global page header/footer, there would be no reason to use `<main>` at all: <main>
<header></header>
<footer></footer>
</main>
Also, I can't really reproduce your initial issue regarding the flexibility of page spacing. You are pretty limited when using classless CSS, but where's the problem using the body selector for that?I know that it is called "MVP", but firstly the term viability can mean different things and secondly there's no indication that the markup is implemented incorrectly. I love to check out example/demo pages from CSS frameworks and it's not uncommon to see glaring semantic errors in the HTML. People just copy everything that is presented to them and you should make sure to give them a good introduction.
>a customer first ethos and not treat them as 'disabled'
That's a weird way of phrasing it. It sounds to me like you try to play accessibility and customer focus against each other. I'd argue that speaking about "customers" instead of "humans" is counterproductive and only some kind of commercial websites like online shops could be compared to a retail businesses. Also, "accessibility" is not a buzzword.
Maybe you could get comfortable with the term universal/inclusive design?
https://sayyeah.com/digital-insights/universal-design-access...
>Text might be below the size Google deems 'accessible'
Which Google guidelines you are referring to?
>Making that text big and chunky might upset designers who want the customer to be browsing by pictures not words.
Do you assume good design and accessibility can't go together? Developing an accessible product generally means that ideally everyone involved has some basic knowledge about a11y. I totally agree that using "SEO" to justify certain decisions is (almost always) a bad idea. Referring to detailed guidelines like the WCAG may be helpful in order to get everyone on board. Obviously designers will get frustrated when told without explanation or context that their design needs to be changed in favor of a11y.
<meta name="viewport" content="width=device-width, initial-scale=1">To get your started, I recommend this short summary about universal design, inclusive design, and accessibility:
https://sayyeah.com/digital-insights/universal-design-access...
* Make sure your navigation is consistent. The left filter links and the about/contact links are missing on many pages. A breadcrumb would help as well.
* The horizontal tabs on the recipe pages aren't really useful, I'd display all content at once. No need to force the users to click several times. Even on smaller viewports it's easier to just scroll.
* The first day immediately gets focused when opening the datepicker. It might be a bit confusing to just hear a number.
* There's enough space to spell the months in full.
* Use semantic abbrevations for weekdays, e.g. `<abbr title="Monday">Mo</abbr>`.
* Use `label`s which refer to the corresponding `select`.
* Use `table` instead of `div`s for the calendar view.
* Use (hidden) text instead of the `title` attribute in buttons.
Furthermore:
* Try using more unique classes for your elements, e.g. '.aeon-datepicker__select' instead of '.select'.
* `cursor: pointer` for buttons would be helpful to see how large the click area is.
What.
(Also, this is your third time promoting this "kit". Maybe read up on the Show HN guidelines[1].)
2. & 3. There seems to be a general misunderstanding with a lot of frameworks about what needs to be customized. Native browser elements are always to be preferred - they are known by the users, accessible, and just work. Custom elements often are a lot more about design than usability and not wanting to "break" the designer's creation. A server-sided validation is of course necessary in both cases nevertheless. Custom client-sided validation can be useful in complex forms though.
3. You’re right, there are examples of both custom and native select elements.
4. Cool, thanks!
[1] e.g. https://oatw.github.io/luda/0.1.x/elements/form#select-field
* _Every_ input needs a <label>.
* Use the `for` attribute to connect labels and inputs.
* Placeholders are not a replacement for labels. You don’t need placeholders just for the sake of it.[2]
* Do not build custom form elements if it can be done without them. There is no need for the dropdown, just use <select>.
* Do use <fieldset> and <legend> to group multiple checkbox/radio inputs.
* Error texts should be connected to the particular input via `aria-describedby`.
* Do use the `required` attribute if form fields are mandatory.
[1]: https://oatw.github.io/luda/0.1.x/elements/form, https://oatw.github.io/luda/0.1.x/patterns/form-group
[2]: https://www.w3.org/WAI/tutorials/forms/instructions/#placeho...