Nesting of paragraph with headings and cite with dynamic content in a VueJS app Background

I added a few items to a codepen that displayed a list of beers. One of them was the citation of the brewer who gave tips. Previously the tips were just generated into a &lt;p&gt; but now I have wrapped it inside a blockquote

Code

&lt;blockquote&gt;
  &lt;p&gt;
    &lt;span class="bright"&gt;Tips from the brewer:&lt;/span&gt; 
    "{{ beer.tips }}"
    &lt;cite&gt;
      &amp;ndash; {{ beer.contributor }} 
      &lt;a style="color: white" :href="`https://www.twitter.com/${beer.twitter}`" target="_blank"&gt;{{beer.twitter}}&lt;/a&gt;
    &lt;/cite&gt;
  &lt;/p&gt;
&lt;/blockquote&gt;  


Demo

My working demo is available on CodePen
I don't know Vue.js then I won't comment about that part.

Overall structure seems OK but maybe few things may be improved. The most obvious one is usage of CSS classes to apply styling without conveying any extra semantic. In your code bright class is applied to text to make it visually distinguishable but:


Name describes the applied style instead of its meaning. If you later decide to use dimmed text then you also need to change class name (or to keep them out-of-sync).
It does not help screen readers to understand what its content is: effectively just a sub-title.
It's applied both to &lt;p&gt;, &lt;span&gt; and...&lt;h3&gt; reinforcing its usage as mere styling instead of carrying any semantic value.


For the tagline I'd use a subheader or a specific class:

&lt;h2&gt;{{ beer.name }}&lt;/h2&gt;
&lt;h2 class="subheader"&gt;{{ beer.tagline }}&lt;/h2&gt;


Alternatively:

&lt;h2&gt;{{ beer.name }}&lt;/h2&gt;
&lt;p class="tagline"&gt;{{ beer.tagline }}&lt;/p&gt;


Note that you can use mixins to avoid CSS duplication then there is no reason to re-use the same class multiple times. Note that you're using &lt;section&gt; for the outer container and there it has little meaning, you may refactor your HTML code to be more HTML5ish:

&lt;div id="app"&gt;
  &lt;header&gt;...&lt;/header&gt;
  &lt;main&gt;
    &lt;div v-if="beers.length === 0" class="loading"&gt;Loading...&lt;/div&gt;
    &lt;article v-for="beer in beers"&gt;
      &lt;aside&gt;
        &lt;img :src="beer.img" height="350" /&gt;
      &lt;/aside&gt;
      &lt;hgroup&gt;
        &lt;h2&gt;{{ beer.name }}&lt;/h2&gt;
        &lt;h2 class="subheader"&gt;{{ beer.tagline }}&lt;/h2&gt;
      &lt;/hgroup&gt;


Note that I'm using &lt;main&gt; as outer container and &lt;article&gt; with its own &lt;hgroup&gt;. What's for? Screen readers (and search engines) now know what each item is, the element conveys a semantic value and you can, also, directly use it in your CSS. Image is actually a side content of the &lt;article&gt; then you can use &lt;aside&gt;.

Refactored this we should look at the other bright elements. Your paragraphs are some text with a title. Exactly what &lt;dl&gt; is for:

&lt;dl&gt;
    &lt;dt&gt;Description:&lt;dt&gt;
    &lt;dd&gt;{{ beer.desc }}&lt;/dd&gt;

    &lt;dt&gt;Tips from the brewer:&lt;dt&gt;
    &lt;dd&gt;...&lt;/dd&gt;
&lt;/dl&gt;


We finally arrived to the &lt;blockquote&gt;. In this case you're quoting a small inline tweet, also note that usually &lt;blockquote&gt; does not contain any extraneous content (besides a &lt;footer&gt; with the &lt;cite&gt; element). What I think is more appropriate for this citations (which are not a separate standalone block of text) is the &lt;q&gt; element:

&lt;dd&gt;
    &lt;q cite="..."&gt;{{ beer.tips }}&lt;/q&gt;
&lt;/dd&gt;


Few important things here: quotation marks should not be part of your HTML, browser already does it (using the appropriate symbols for the current language - which BTW you should add to your HTML). Also note the cite attribute to reference the source (if it's a twitter than you have an URL to link). &lt;cite&gt; element can follow inside &lt;dd&gt;.

You can (and probably should) style &lt;h3&gt; directly without using bright. You may also like (if required by your CSS) to wrap each section with &lt;section&gt; (in this case you may have &lt;hgroup&gt; instead of the &lt;dl&gt; list).

You may consider to use microdata for some of your content (beer name and author of the tweet).

JS local variables in addBeer() can be const instead of let.



I see absolutely no reason (for this kind of content) to do not support accessibility. It's more complex than one paragraph in this questionthen just to refer to official W3C documentation.