These types of non-descriptive links are not helpful to screen reader users.
Screen reader users frequently navigate web pages, using the TAB key, through actionable items such as links, buttons and form controls.
...
The button/link text alone should convey the function and purpose of the link.
Best Practice
Best practice is to try and provide descriptive link/button labels by default.
However, in situations when this is not possible the following techniques can be used.
Use aria-labelledby
To solve this issue for screen reader users you can use the aria-labelledby attribute to associate the non-descriptive link label ("Learn more..." "More..." "See more", etc) with the text of the heading of the preceding section.
...
The speech to input user will not know what the aria-label is as it is not visible to them. However if the aria-label starts out with the default button label, "Learn more about London Breed", the speech recognition software will be able to recognize that button label.
Best Practice
Best practice is to try and provide descriptive link/button labels by default. However, in situations when this is not possible these techniques can be used.